| 3 | Approval of the Agenda | |
|---|---|---|
| R3-226100 | RAN3#118 Meeting Agenda | RAN3 Chair |
| 4 | Approval of the minutes from previous meetings | |
| R3-226101 | RAN3#117bis-e Meeting report | ETSI-MCC |
| 5 | Documents for immediate consideration | |
| R3-226188 | Guidelines for RAN3 f2f Meetings with Remote Access | RAN3 Chair, RAN3 Vice-Chairs |
| 8.1 | New Incoming LSs | |
| R3-226163 | Response LS on LCS framework for Network verified UE location (NTN) | SA2 |
| R3-226164 | LS Out on Positioning Reference Units | SA2 |
| R3-226165 | LS on LPHAP information delivery to RAN | SA2 |
| R3-226167 | Progress and open issues for NPN enhancements in Rel-18 | SA2 |
| R3-226168 | LS on Time Synchronization Status notification towards UE(s) | SA2 |
| R3-226169 | LS on UL scenario of reactive RAN feedback for burst sending time adjustment | SA2 |
| R3-226170 | LS On long eDRX support for RRC_INACTIVE | SA2 |
| R3-226173 | LS on XR and Media Services | SA2 |
| R3-226177 | Reply LS on RAN dependency of FS_eNS_Ph3 | RAN2 |
| R3-226212 | Analysis of Long eDRX Support for RRC Inactive | Nokia, Nokia Shanghai Bell |
| R3-226213 | Reply LS on Long eDRX Support for RRC Inactive | Nokia, Nokia Shanghai Bell |
| R3-226214 | Support of long eDRX for RRC INACTIVE state | Nokia, Nokia Shanghai Bell |
| R3-226215 | Support of long eDRX for RRC INACTIVE state | Nokia, Nokia Shanghai Bell |
| R3-226235 | Discussion on Time Synchronization Status notification towards UE(s) | Nokia, Nokia Shanghai Bell |
| R3-226236 | [Draft] Reply LS on Time Synchronization Status notification towards UE(s) | Nokia, Nokia Shanghai Bell |
| R3-226240 | Discussion on Long eDRX support for RRC_INACTIVE | ZTE |
| R3-226241 | CR38.413 to support Long eDRX support for RRC_INACTIVE | ZTE |
| R3-226242 | CR38.423 to support Long eDRX support for RRC_INACTIVE | ZTE |
| R3-226243 | CR38.473 to support Long eDRX support for RRC_INACTIVE | ZTE |
| R3-226256 | [Draft] Reply LS on long eDRX support for RRC_INACTIVE | ZTE |
| R3-226346 | Discussion on congestion information for XR and Media Services | Huawei |
| R3-226347 | [DRAFT] Reply LS on XR and Media Services | Huawei |
| R3-226400 | Time Synchronization Status notification towards UE(s) | Huawei |
| R3-226401 | [Draft] Reply LS on Time Synchronization Status notification towards UE(s) | Huawei |
| R3-226424 | Discussion on RAN3 impact of XR Service | Lenovo |
| R3-226449 | Current status on Rel-18 NPN discussions and outlook to expected specification work in RAN WG3 | Ericsson |
| R3-226493 | Analysis of L4S aspects | Ericsson, Deutsche Telekom, T-Mobile USA, Nokia, Nokia Shanghai Bell, Charter, Telstra |
| R3-226494 | Reply LS on XR and Media Services | Ericsson |
| R3-226509 | RAN3 reply on 5GS time synchronization status | Ericsson |
| R3-226510 | [Draft] LS reply on Time Synchronization Status notification towards UE(s) | Ericsson |
| R3-226544 | Proposition for RAN3 feedback to SA2 on long eDRX support for RRC_INACTIVE | Ericsson |
| R3-226545 | [Draft] LS On long eDRX support for RRC_INACTIVE | Ericsson |
| R3-226621 | Discussion on long eDRX support for RRC_INACTIVE | Huawei |
| R3-226622 | [draft] Reply LS on long eDRX support for RRC_INACTIVE | Huawei |
| R3-226623 | NGAP CR on long eDRX support for RRC_INACTIVE | Huawei |
| R3-226640 | Discussion on XR and Media Services | ZTE |
| R3-226641 | [DRAFT] Reply LS on XR and Media Services | ZTE |
| R3-226650 | Draft Reply to LS R3-226168 Time Synchronization Status notification towards UE | Qualcomm Incorporated |
| R3-226651 | Draft Reply to LS R3-226170 long eDRX support for RRC_INACTIVE | Qualcomm Incorporated |
| R3-226652 | CR for TS38.3413 on CN based MT handling for RedCap UEs with long eDRX | Qualcomm Incorporated |
| R3-226653 | RRC_Inactive with long eDRX Support for RedCap | Qualcomm Incorporated |
| R3-226717 | Discussion on long eDRX for RRC_INACTIVE | CATT |
| R3-226722 | Discussion on Time Synchronization Status notification | ZTE |
| R3-226723 | [Draft] Reply LS on Time Synchronization Status notification | ZTE |
| R3-226735 | Reply LS on XR and Media Services | Xiaomi |
| R3-226766 | Response to R3-226400, R3-226509, and R3-226722 | Nokia, Nokia Shanghai Bell |
| R3-226774 | Reply LS on Time Synchronization Status notification towards UE(s) | ZTE |
| R3-226775 | Reply LS on XR and Media Services | Ericsson |
| R3-226776 | Reply LS on long eDRX support for RRC_INACTIVE | Nokia, Nokia Shanghai Bell |
| R3-226877 | Reply LS on XR and Media Services | Ericsson |
| R3-226885 | Reply LS on XR and Media Services | Ericsson |
| 8.2 | LSin received during the meeting | |
| R3-226914 | LS to capture Text Proposal for TR 38.859 | RAN2 |
| 8.3 | Left over LSs / pending actions | |
| R3-226216 | Slice List And Priority Information for Random Access in RRC Connected State | Nokia, Nokia Shanghai Bell |
| R3-226217 | Correction of slice-based RACH configuration at handover | Nokia, Nokia Shanghai Bell |
| R3-226218 | Correction of slice-based RACH configuration at handover | Nokia, Nokia Shangha Bell |
| R3-226219 | Reply LS on Slice List and Priority Information for Cell Re-selection and Random Access | Nokia, Nokia Shanghai Bell |
| R3-226765 | Response to R3-226216 | ZTE Corporation |
| 9.2.1 | RVQoE | |
| R3-226468 | [Draft] LS Reply to Questions on RAN Visible QoE | Ericsson |
| R3-226624 | Further discussion on RAN visible QoE | Huawei |
| R3-226625 | [draft] Reply LS on questions on RAN visible QoE | Huawei |
| R3-226718 | Discussion on RVQoE left issue | ZTE |
| R3-226757 | (draftCR TS 38.300) on RAN visible QoE | Ericsson |
| R3-226778 | Reply LS on questions on RAN visible QoE | Huawei |
| R3-226835 | draftCR to TS 38.300 on RAN visible QoEE | Ericsson |
| 9.2.2 | SONMDT | |
| R3-226289 | Correction on LTE UE RLF Report in TS38.423 | China Telecom,CATT,ZTE |
| R3-226290 | Correction on LTE UE RLF Report in TS38.423 | China Telecom, CATT, ZTE |
| R3-226291 | Correction on UE RLF Report in TS38.423 | CATT, China Telecom, ZTE |
| R3-226306 | [draft] LS on Excess Packet Delay for MDT | Huawei |
| R3-226469 | Correction on MLB function in TS38.401 | ZTE, China Telecom, China Unicom |
| R3-226470 | Correction on Resource Status Reporting procedure over F1 | ZTE |
| R3-226501 | Corrections related to Excess Packet Delay | Ericsson, AT&T, Deutsche Telekom, Huawei, CATT, BT |
| R3-226502 | XnAP Corrections related to Excess Packet Delay | Ericsson, AT&T, Deutsche Telekom, Huawei, CATT, BT |
| R3-226503 | Correction related to Management Based MDT PLMN Modification List | Ericsson |
| R3-226533 | Correction of Last Visited NG-RAN Cell Information | Nokia, Nokia Shanghai Bell |
| R3-226534 | Correction of Last Visited NG-RAN Cell Information | Nokia, Nokia Shanghai Bell |
| R3-226535 | Correction of Last Visited NG-RAN Cell Information | Nokia, Nokia Shanghai Bell |
| R3-226537 | Handling of UL PDCP Excess Packet Delay measurement configuration for MDT in NGAP and XnAP | Nokia, Nokia Shanghai Bell |
| R3-226635 | NGAP Corrections related for Excess Packet Delay | CATT, Ericsson, AT&T, DT, Huawei |
| R3-226638 | Discussion on corrections for UE History Information | ZTE, Samsung, Lenovo, China Telecom |
| R3-226639 | Correction for TS 37.340 on UHI MR-DC | ZTE, Samsung, Lenovo, China Telecom |
| R3-226779 | CB: #5_R17SONMDT - Summary of email discussion | ZTE - moderator |
| R3-226820 | Correction on MLB function in TS38.401 | ZTE, China Telecom, China Unicom |
| R3-226821 | Correction on Resource Status Reporting procedure over F1 | ZTE |
| R3-226827 | [draft] LS on Excess Packet Delay for MDT | Huawei |
| R3-226830 | NGAP Corrections related for Excess Packet Delay | CATT, Ericsson, AT&T, Deutsche Telekom, Huawei, Nokia, Nokia Shanghai Bell |
| R3-226842 | XnAP Corrections related to Excess Packet Delay | Ericsson, AT&T, Deutsche Telekom, Huawei, CATT, BT |
| R3-226843 | Correction related to Management Based MDT PLMN Modification List | Ericsson |
| R3-226849 | XnAP Corrections related to Excess Packet Delay | Ericsson, AT&T, Deutsche Telekom, Huawei, CATT, BT, Nokia, Nokia Shanghai Bell |
| R3-226851 | NGAP Corrections related for Excess Packet Delay | CATT, Ericsson, AT&T, Deutsche Telekom, Huawei, Nokia, Nokia Shanghai Bell |
| R3-226853 | Correction on LTE UE RLF Report in TS38.423 | China Telecom, CATT, ZTE |
| R3-226854 | Correction on UE RLF Report in TS38.423 | CATT, China Telecom, ZTE |
| R3-226872 | NGAP Corrections related for Excess Packet Delay | CATT, Ericsson, AT&T, Deutsche Telekom, Huawei, Nokia, Nokia Shanghai Bell |
| R3-226873 | LS on Excess Packet Delay for MDT | Huawei |
| R3-226874 | XnAP Corrections related to Excess Packet Delay | Ericsson, AT&T, Deutsche Telekom, Huawei, CATT, BT, Nokia, Nokia Shanghai Bell |
| R3-226879 | NGAP Corrections related for Excess Packet Delay | CATT, Ericsson, AT&T, Deutsche Telekom, Huawei, Nokia, Nokia Shanghai Bell |
| R3-226901 | Correction related to Management Based MDT PLMN Modification List | Ericsson |
| R3-226904 | Correction on Resource Status Reporting procedure over F1 | ZTE |
| R3-226905 | XnAP Corrections related to Excess Packet Delay | Ericsson, AT&T, Deutsche Telekom, Huawei, CATT, BT, Nokia, Nokia Shanghai Bell |
| R3-226906 | Correction related to Management Based MDT PLMN Modification List | Ericsson |
| 9.2.3 | IAB | |
| R3-226250 | Clarification on IAB TNL Address Request IE | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm, ZTE, CATT, Ericsson |
| R3-226348 | Correction on resource configuration for IAB | Huawei, Lenovo, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-226349 | Correction on IAB STC Info | Huawei |
| R3-226386 | Correction to TS 38.473 on RB Set Configuration | ZTE |
| R3-226417 | (CR TS 38.473) Correction to NR Carrier List | Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-226768 | Response to R3-226386 | Ericsson Japan K.K. |
| R3-226780 | Correction on IAB STC Info | Huawei |
| R3-226781 | LS on RB set configuration | ZTE |
| R3-226782 | (CR TS 38.473) Correction to NR Carrier List | Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-226783 | (CR TS 38.473) Correction to NR Carrier List | Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-226784 | (CR TS 38.473) Correction to NR Carrier List | Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-226806 | Rel-16 Correction to NR Carrier List | Ericsson |
| R3-226807 | Rel-17 Correction to NR Carrier List | Ericsson |
| 9.2.4 | Positioning | |
| R3-226181 | Reply LS on SRS-PosRRC-InactiveConfig configuration signalling | RAN2 |
| R3-226182 | Reply LS on applicability of timing error margin of Rx TEG | RAN2 |
| R3-226237 | Timing Error Margin for UE/TRP TEGs | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, CATT |
| R3-226238 | Correction on presence of timing error margin for TRP TEGs | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, CATT |
| R3-226239 | Correction on presence of timing error margin for TRP TEGs | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, CATT |
| R3-226293 | Discussion on the NG-RAN Access Point Position | Huawei, CMCC, China Unicom |
| R3-226294 | Correction on the NG-RAN Access Point Position | Huawei, CMCC, China Unicom |
| R3-226295 | Correction on the NG-RAN Access Point Position | Huawei |
| R3-226296 | Correction on the NG-RAN Access Point Position | Huawei |
| R3-226297 | Correction on the NG-RAN Access Point Position | Huawei, CMCC, China Unicom |
| R3-226298 | Correction on the NG-RAN Access Point Position | Huawei |
| R3-226299 | Stage 2 text addition on UE context management function for positioning | Huawei, CMCC, China Unicom |
| R3-226672 | Discussion and support based on the reply LS R3-226181 from RAN2 | Intel Corporation, Ericsson, Google, CATT, ZTE, Qualcomm, Huawei, LGE, Samsung, Lenovo |
| R3-226673 | Rel-17 ePos correction for retrieving SRS configurations for UL positioning in a CU-DU split architecture | Intel Corporation, Ericsson, Google, CATT, ZTE, Qualcomm, Huawei, LGE, Samsung, Lenovo |
| R3-226733 | Discussion on Reply LS on SRS-PosRRC-InactiveConfig configuration signalling | Xiaomi |
| R3-226769 | Response to R3-226733 | Intel Corporation |
| R3-226785 | Stage 2 text addition on UE context management function for positioning | Huawei, CMCC, China Unicom |
| R3-226878 | Rel-17 ePos correction for retrieving SRS configurations for UL positioning in a CU-DU split architecture | Intel Corporation, Ericsson, Google, CATT, ZTE, Qualcomm, Huawei, LGE, Samsung, Lenovo, Xiaomi |
| 9.2.5 | MBS | |
| R3-226161 | Reply LS on Multicast MBS session Deactivation and Reactivation | SA2 |
| R3-226162 | Reply LS on shared NG-U Termination among gNBs | SA2 |
| R3-226220 | Correction of MBS data forwarding | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated |
| R3-226221 | Correction of MBS data forwarding | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated |
| R3-226222 | Correction of MBS multicast HFN SN Initialisation | Nokia, Nokia Shanghai Bell, CATT, Orange, Qualcomm Incorporated |
| R3-226223 | Correction of MBS multicast HFN SN Initialisation | Nokia, Nokia Shanghai Bell, CATT, Orange, Qualcomm Incorporated |
| R3-226224 | LS on Multicast HFN/SN Initialization for Inactive Multicast Sessions | Nokia, Nokia Shanghai Bell, CATT, Orange, Qualcomm Incorporated |
| R3-226225 | Correction of MBS shared CU UP | Nokia, Nokia Shanghai Bell, Ericsson, Orange |
| R3-226226 | Correction of MBS shared CU UP | Nokia, Nokia Shanghai Bell, Ericsson, Orange |
| R3-226333 | Correction on NR MBS over F1AP | Huawei, CBN, Qualcomm Incorporated, Lenovo, Nokia, Nokia Shanghai Bell |
| R3-226334 | Inclusion of MBS Parameters in PDU Session Management procedures | Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo |
| R3-226335 | Clarification on NID handling within the MBS Session ID | Huawei, CBN, China Unicom, Lenovo |
| R3-226336 | Clarification on NID handling within the MBS Session ID | Huawei, CBN, China Unicom, Lenovo |
| R3-226337 | Correction on MRB QoS Information | Huawei, CBN, Qualcomm Incorporated, Lenovo, Nokia, Nokia Shanghai Bell |
| R3-226338 | Delay issue on initialization of initialRX-DELIV | Huawei, CBN, China Unicom |
| R3-226339 | Correction on the delay issue on initialization of initialRX-DELIV | Huawei, CBN, China Unicom |
| R3-226340 | [Draft] LS on the delay issue on initialization of initialRX-DELIV | Huawei |
| R3-226356 | Introduction of ongoing broadcast service in XnAP | CATT,Nokia, Nokia Shanghai Bell,Huawei,Qualcomm |
| R3-226357 | Discussion on MRB PDCP count “wrap around” problem | CATT |
| R3-226358 | Correction on MRB PDCP count “wrap around” problem | CATT |
| R3-226446 | Correction of multicast session activation related procedure text | Ericsson, AT&T, China Unicom |
| R3-226447 | Introduction of multicast MBS session status in Multicast Context Management messages | Ericsson, AT&T, China Unicom |
| R3-226448 | MC Bearer Context Setup without MBS QoS flow information available | Ericsson, AT&T, China Unicom |
| R3-226450 | Activation and Admission Control | Ericsson, AT&T, China Unicom |
| R3-226451 | Correcting an E1AP error in E1AP | Ericsson, AT&T, China Unicom, CATT |
| R3-226452 | MC Bearer Context Setup without MBS QoS flow information available | Ericsson, AT&T, China Unicom, CATT |
| R3-226453 | Comments on open issues regarding PDCP COUNT handling on network side for multicast MRBs | Ericsson |
| R3-226488 | Correction of MBS Session Activation | Nokia, Nokia Shanghai Bell, Orange, Huawei, Qualcomm Incorporated |
| R3-226489 | Correction of TMGI Handling | Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated |
| R3-226490 | Solution for MRB PDCP Wrap Around | Nokia, Nokia Shanghai Bell |
| R3-226737 | Provision of MRB configuration to gNB-CU in the response message to UE context setup and gNB-CU initiated modification | ZTE, Huawei, Qualcomm, Lenovo, CATT, Nokia, Nokia Shanghai Bell |
| R3-226767 | Response to R3-226451, R3-226452 and R3-226334 | ZTE |
| R3-226786 | CB: #9_MBSHFN_SN - Summary of email discussion | Ericsson - moderator |
| R3-226787 | Correction on NR MBS over F1AP | Huawei, CBN, Qualcomm Incorporated, Lenovo, Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R3-226788 | CB: # 11_MBSQoS - Summary of email discussion | Huawei - moderator |
| R3-226789 | Correction on MRB QoS Information | Huawei, CBN, Qualcomm Incorporated, Lenovo, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-226838 | [DRAFT] LS on potential de-synchronisation of a multicast MRB’s PDCP HFN and SN” | Ericsson |
| R3-226845 | MC Bearer Context Setup without MBS QoS flow information available | Ericsson, AT&T, China Unicom, CATT, Nokia, Nokia Shanghai Bell, Huawei, Qualcomm, Lenovo, ZTE |
| R3-226875 | LS on potential de-synchronisation of a multicast MRB’s PDCP HFN and SN | Ericsson |
| R3-226903 | LS on potential de-synchronisation of a multicast MRB’s PDCP HFN and SN | Ericsson |
| 9.2.6 | Gap Configuration | |
| R3-226402 | Gap Association Information for concurrent gap configuration [NR_MG_enh-Core] | Huawei, Deutsche Telekom |
| R3-226471 | Further discussion on concurrent gap configuration over F1 | ZTE, China Telecom, China Unicom |
| R3-226472 | Correction on concurrent measurement gap configuration over F1 [NR_MG_enh-Core] | ZTE, China Telecom, China Unicom |
| 9.2.7 | Others | |
| R3-226178 | Response to “Reply to LS on UE capability signaling for IoT-NTN” | RAN2 |
| R3-226189 | Additional ULI provision with PScell information [PSCellID-Setup-Modify] | Nokia, Nokia Shanghai Bell, Vodafone, Ericsson |
| R3-226190 | Additional ULI provision with PScell information [PSCellID-Setup-Modify] | Nokia, Nokia Shanghai Bell, Vodafone, Ericsson |
| R3-226191 | Clarification of the desired buffer size in case of retransmissions [DesBufRetrans] | Nokia, Nokia Shanghai Bell, Huawei, Ericsson |
| R3-226199 | Additional indicator for CHO-CPC coordination | Nokia, Nokia Shanghai Bell |
| R3-226200 | Additional indicator for CHO-CPC coordination | Nokia, Nokia Shanghai Bell |
| R3-226228 | Handling interaction between CPC cancel and SN release | Ericsson, Lenovo, ZTE, Google Inc., Intel Corporation |
| R3-226229 | Interaction between CPC Cancel and SN Release | Ericsson, Lenovo, ZTE, Google Inc., Intel Corporation |
| R3-226244 | Clarification on direct data forwarding for SN initiated CPC to TS37.340 | ZTE, CATT, Huawei |
| R3-226245 | Discussion on DAPS status transfer | ZTE, CATT, China Unicom, China Telecom |
| R3-226246 | CR for DAPS state transfer in case of split gNB deployment to Rel-16 38.473 | ZTE, CATT, China Unicom, China Telecom |
| R3-226247 | CR for DAPS state transfer in case of split gNB deployment to Rel-17 38.473 | ZTE, CATT, China Unicom, China Telecom |
| R3-226251 | Direct or indirect early data forwarding in SN initiated inter-SN CPC | Huawei, Deutsche Telekom, ZTE, CATT |
| R3-226252 | Direct early data forwarding in SN initiated inter-SN CPC | Huawei, Deutsche Telekom, ZTE, CATT, Nokia, Nokia Shanghai Bell |
| R3-226253 | Direct early data forwarding in SN initiated inter-SN CPC | Huawei, Deutsche Telekom, ZTE, CATT, Nokia, Nokia Shanghai Bell |
| R3-226254 | PDCP PDU early transmission in CPAC | Huawei, Lenovo, China Telecom |
| R3-226255 | Correction on providing paritial UE context in small data transmission | Huawei, China Telecom, Samsung, ZTE |
| R3-226259 | SL relay corrections | Huawei, Nokia, Nokia Shanghai Bell, CATT, Qualcomm, Samsung |
| R3-226260 | SL relay corrections | Huawei, Nokia, Nokia Shanghai Bell, CATT, Qualcomm, Samsung |
| R3-226261 | SL relay corrections | Huawei, Nokia, Nokia Shanghai Bell, CATT, Qualcomm, Samsung |
| R3-226286 | Left issues about SL relay in Rel-17 | CATT, Samsung, Huawei, CMCC |
| R3-226287 | Correction to 38.401 for SL relay (R17) | CATT, Samsung, Huawei, CMCC |
| R3-226288 | Correction to 38.473 for SL relay (R17) | CATT, Samsung, Huawei, CMCC |
| R3-226292 | Support of DC Location for two or more UL CCs in Split architecture | China Telecom, ZTE, CATT |
| R3-226307 | Support of DC Location for two UL CCs in Split architecture | China Telecom, ZTE, CATT |
| R3-226308 | Support of DC Location for two UL CCs in Split architecture | China Telecom,ZTE,CATT |
| R3-226341 | Correction on Missing Criticality Diagnostics over F1AP | Huawei, BT, Deutsche Telekom, Orange |
| R3-226342 | Correction on Missing Criticality Diagnostics over F1AP | Huawei, BT, Deutsche Telekom, Orange |
| R3-226343 | Correction on Missing Criticality Diagnostics over F1AP | Huawei, BT, Deutsche Telekom, Orange |
| R3-226344 | Correction on Missing Criticality Diagnostics over W1AP | Huawei, BT, Deutsche Telekom, Orange |
| R3-226345 | Correction on Missing Criticality Diagnostics over W1AP | Huawei, BT, Deutsche Telekom, Orange |
| R3-226370 | Clarifications on prepared PSCell addition by candidate SN | NEC, ZTE |
| R3-226371 | Clarifications on prepared PSCell addition by candidate SN | NEC, ZTE |
| R3-226394 | Correction of on-demand SI for connected UE | Huawei, Orange, Deutsche Telekom, BT, Qualcomm |
| R3-226395 | Correction of on-demand SI for connected UE | Huawei, Orange, Deutsche Telekom, BT, Qualcomm |
| R3-226396 | Introduction of two PHR mode [NR_feMIMO-Core] | Huawei, Deutsche Telekom |
| R3-226408 | Correction on SCG reconfiguration when MN initiated conditional reconfiguration is prepared | Lenovo, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, CATT, ZTE, Intel Corporation, Google |
| R3-226409 | Correction on SCG reconfiguration when MN initiated conditional reconfiguration is prepared | Lenovo, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, CATT, ZTE, Intel Corporation, Google |
| R3-226410 | Correction on SCG reconfiguration when MN initiated conditional reconfiguration is prepared | Lenovo, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, CATT, ZTE, Intel Corporation, Google |
| R3-226460 | Discussion on MCG configuration during CPAC | Google Inc. |
| R3-226461 | Correction to conditional MCG configuration in CPAC | Google Inc. |
| R3-226504 | Restriction of NIA0 algorithm in gNB-CU-UP | Ericsson |
| R3-226505 | Restriction of NIA0 algorithm in gNB-CU-UP | Ericsson |
| R3-226506 | Restriction of NIA0 algorithm in gNB-CU-UP | Ericsson |
| R3-226511 | Location Reporting Correction | Ericsson |
| R3-226512 | Location Reporting Correction | Ericsson |
| R3-226536 | Remote Interference Management - issue on RIM-RS boundary alignment | Nokia, Nokia Shanghai Bell |
| R3-226546 | Support of NCD-SSB RedCap requirements in F1AP | Ericsson, CATT, China Telecom |
| R3-226547 | Correction to support NCD-SSB RedCap requirements in F1AP | Ericsson, CATT, China Telecom |
| R3-226549 | R17 CR to TS38.473 on Support of DC Location for more carriers in Split architecture | ZTE, China Telecom |
| R3-226550 | Uplink Tx DC locations for two carriers | Huawei, Deutsche Telekom, CMCC, BT |
| R3-226551 | Uplink Tx DC locations for more carriers [NR_RF_FR2_req_enh2-Core] | Huawei, Deutsche Telekom, CMCC, BT |
| R3-226552 | Correction of NR PRACH Configuration List for NR-U | Huawei, Deutsche Telekom, China Telecom |
| R3-226553 | Correction of NR PRACH Configuration List for FR2-2 | Huawei, Deutsche Telekom, China Telecom |
| R3-226561 | VoNR supportive for UE capability Check procedure in NGAP | ZTE, China Telecom, China Unicom |
| R3-226562 | CR for VoNR supportive for UE capability Check procedure(R16) | ZTE, China Telecom, China Unicom |
| R3-226563 | CR for VoNR supportive for UE capability Check procedure(R17) | ZTE, China Telecom, China Unicom |
| R3-226567 | Correction of NR PRACH Configuration List for NR-U | Huawei, Deutsche Telekom, China Telecom |
| R3-226631 | Correction on the user consent in PATH SWITCH REQUEST ACKNOWLEDGE message (REL-17) | CATT, Huawei, Ericsson, SAMSUNG, ZTE |
| R3-226632 | Correction on the user consent in PATH SWITCH REQUEST ACKNOWLEDGE message (REL-16) | CATT, Ericsson |
| R3-226643 | Remaining issue for SN-MN awareness on conditional reconfiguration validity | CATT |
| R3-226644 | Introducing cell direction over Xn interface | Huawei |
| R3-226645 | Introducing cell direction over Xn interface | Huawei |
| R3-226678 | Rel-17 early data forwarding support in SN-initiated inter-SN CPC | Intel Corporation |
| R3-226679 | Rel-17 early data forwarding support in SgNB-initiated inter-SN CPC | Intel Corporation |
| R3-226680 | Discussions for what would be the right way to inform S-SN that MN-initiated inter-SN CPC has been successfully configured to the UE | Intel Corporation |
| R3-226681 | Rel-17 correction for notification of "CPC has been successfully configured to the UE" toward S-SN in MN-initiated inter-SN CPC | Intel Corporation |
| R3-226682 | Rel-17 correction for notification of "CPC has been successfully configured to the UE" toward S-SN in MN-initiated inter-SN CPC | Intel Corporation |
| R3-226683 | Rel-17 correction for notification of "CPC has been successfully configured to the UE" toward S-SN in MN-initiated inter-SN CPC | Intel Corporation |
| R3-226686 | CR for TS36.423 on Extending NR Operation to 71GHz | China Telecom, Ericsson |
| R3-226690 | Discussion on remaining issues for SL relay | ZTE |
| R3-226691 | Correction to TS 38.473 on SL relay | ZTE |
| R3-226697 | Remaining issue for SN-MN awareness on conditional reconfiguration validity | CATT |
| R3-226698 | Correction on SN-MN awareness on conditional reconfiguration validity | CATT |
| R3-226699 | Correction on SN-MN awareness on conditional reconfiguration validity | CATT |
| R3-226700 | Correction on SN-MN awareness on conditional reconfiguration validity | CATT |
| R3-226724 | Including data forwarding addresses for multiple T-SNs in the SN Change Confirm message in the SN-initiated inter-SN CPC procedure | Samsung |
| R3-226729 | Correction on coarse UE location reporting for TS 38.300 | Xiaomi, Apple, CAICT, CMCC |
| R3-226759 | Correction on the MN initiated SN Modification procedure | Ericsson |
| R3-226764 | Response to R3-226408 and R3-Response to R3-226408 and R3-226698 | ZTE |
| R3-226790 | CR for TS36.423 on Extending NR Operation to 71GHz [ENDC_71GHz] | China Telecom, Ericsson, Huawei |
| R3-226793 | Correction to 38.473 for SL relay (R17) | CATT, Samsung, Huawei, CMCC |
| R3-226795 | Interaction between CPC Cancel and SN Release | Ericsson, Lenovo, ZTE, Google Inc., Intel Corporation |
| R3-226796 | CB: # 13_SCG reconfiguration - Summary of email discussion | Lenovo - moderator |
| R3-226797 | CB: # 14_Dataforwarding_MultipleTSNs - Summary of email discussion | Huawei - moderator |
| R3-226798 | CB: # 15_Indicator_CHO-CPC - Summary of email discussion | Nokia - moderator |
| R3-226799 | CB: # 16_MCGConfigF1 - Summary of email discussion | Google -moderator |
| R3-226800 | Clarifications on prepared PSCell addition by candidate SN | NEC, ZTE |
| R3-226801 | CR for DAPS state transfer in case of split gNB deployment to Rel-16 38.473 | ZTE, CATT, China Unicom, China Telecom, Huawei, Intel Corporation |
| R3-226802 | CR for DAPS state transfer in case of split gNB deployment to Rel-17 38.473 | ZTE, CATT, China Unicom, China Telecom, Huawei, Intel Corporation |
| R3-226815 | SL relay corrections | Huawei, Nokia, Nokia Shanghai Bell, CATT, Qualcomm, Samsung |
| R3-226816 | SL relay corrections | Huawei, Nokia, Nokia Shanghai Bell, CATT, Qualcomm, Samsung |
| R3-226817 | Additional ULI provision with PScell information | Nokia, Nokia Shanghai Bell, Vodafone, Ericsson |
| R3-226818 | Additional ULI provision with PScell information | Nokia, Nokia Shanghai Bell, Vodafone, Ericsson |
| R3-226819 | Correction to conditional MCG configuration in CPAC | Google Inc. |
| R3-226832 | Clarification of the desired buffer size in case of retransmissions [DesBufRetrans] | Nokia, Nokia Shanghai Bell, Huawei, Ericsson, ZTE |
| R3-226837 | Correction of on-demand SI for connected UE | Huawei, Orange, Deutsche Telekom, BT, Qualcomm |
| R3-226839 | Correction on providing paritial UE context in small data transmission | Huawei, China Telecom, Samsung, ZTE, Ericsson, Intel Corporation, LG Electronics |
| R3-226855 | Uplink Tx DC locations for two carriers | Huawei, Deutsche Telekom, CMCC, BT, China Telecom, ZTE, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-226856 | Support of DC Location for two UL CCs in Split architecture | China Telecom, ZTE, CATT, Huawei, Ericsson |
| R3-226857 | R17 CR to TS38.473 on Support of DC Location for more carriers in Split architecture | ZTE, China Telecom, , Nokia, Nokia Shanghai Bell, Huawei, Ericsson |
| R3-226863 | Correction to 38.401 for SL relay (R17) | CATT, Samsung, Huawei, CMCC |
| R3-226866 | SOD on topic of prepared PSCell addition by candidate SN for SN initiated CPC | NEC |
| R3-226867 | Clarifications on prepared PSCell addition by candidate SN | NEC |
| R3-226870 | Additional indicator for CHO-CPC coordination | Nokia, Nokia Shanghai Bell |
| R3-226871 | Additional indicator for CHO-CPC coordination | Nokia, Nokia Shanghai Bell |
| R3-226880 | Correction to 38.473 for SL relay (R17) | CATT, Samsung, Huawei, CMCC |
| R3-226882 | Support of DC Location for two UL CCs in Split architecture | China Telecom, ZTE, CATT, Huawei, Ericsson |
| R3-226886 | Clarification on direct data forwarding for SN initiated CPC to TS37.340 | ZTE, CATT, Huawei |
| R3-226888 | Support of DC Location for two UL CCs in Split architecture | China Telecom, ZTE, CATT, Huawei, Ericsson |
| R3-226891 | Rel-17 early data forwarding support in SN-initiated inter-SN CPC | Intel Corporation |
| R3-226892 | Rel-17 early data forwarding support in SgNB-initiated inter-SN CPC | Intel Corporation |
| R3-226894 | Direct early data forwarding in SN initiated inter-SN CPC | Huawei, Deutsche Telekom, ZTE, CATT, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-226895 | Direct early data forwarding in SN initiated inter-SN CPC | Huawei, Deutsche Telekom, ZTE, CATT, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-226896 | Correction on providing paritial UE context in small data transmission | Huawei, China Telecom, Samsung, ZTE, Ericsson, Intel Corporation, LG Electronics, Nokia, Nokia Shanghai Bell |
| R3-226899 | SL relay corrections | Huawei, Nokia, Nokia Shanghai Bell, CATT, Qualcomm, Samsung |
| R3-226907 | Support of DC Location for two UL CCs in Split architecture | China Telecom,ZTE,CATT,Huawei,Ericsson, Nokia, Nokia Shanghai Bell |
| R3-226908 | Uplink Tx DC locations for two carriers | Huawei, Deutsche Telekom, CMCC, BT, China Telecom, ZTE, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-226909 | R17 CR to TS38.473 on Support of DC Location for more carriers in Split architecture | ZTE, China Telecom, , Nokia, Nokia Shanghai Bell, Huawei, Ericsson |
| R3-226915 | Correction to 38.473 for SL relay (R17) | CATT, Samsung, Huawei, CMCC, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-226917 | Clarification on direct data forwarding for SN initiated CPC to TS37.340 | ZTE, CATT, Huawei, Ericsson, Intel Corporation |
| R3-226919 | Additional indicator for CHO-CPC coordination | Nokia, Nokia Shanghai Bell, Intel Corporation, ZTE, Lenovo, Huawei, Ericsson |
| R3-226920 | Additional indicator for CHO-CPC coordination | Nokia, Nokia Shanghai Bell, Intel Corporation, ZTE, Lenovo, Huawei, Ericsson |
| R3-226921 | Correction to 38.473 for SL relay (R17) | CATT, Samsung, Huawei, CMCC, Nokia, Nokia Shanghai Bell, Ericsson |
| 9.3 | Endorsed CRs from RAN3#117bis-e | |
| R3-226111 | Further correction to Report Caracteristics | Nokia, Nokia Shanghai Bell, ZTE, Ericsson, CMCC, CATT, China Unicom, China Telecom, Deutsche Telekom |
| R3-226112 | Further correction to Report Caracteristics | Nokia, Nokia Shanghai Bell, ZTE, Ericsson, CMCC, CATT, China Unicom, China Telecom, Deutsche Telekom |
| R3-226113 | Correction of Timing Error Margin | Ericsson, CATT, Nokia, Nokia Shanghai Bell, ZTE |
| R3-226114 | Correction of Positioning Information Transfer function | Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-226115 | Correction of Timing Error Margin for F1AP | CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-226116 | CR to 38.455 on SRS periodicity | Huawei, China Unicom, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, CATT, Deutsche Telekom |
| R3-226117 | CR to 38.455 on SRS periodicity | Huawei, China Unicom, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, CATT, Deutsche Telekom |
| R3-226118 | CR to 38.473 on SRS periodicity | Huawei, China Unicom, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, CATT, Deutsche Telekom |
| R3-226119 | CR to 38.473 on SRS periodicity | Huawei, China Unicom, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, CATT, Deutsche Telekom |
| R3-226120 | Correction of ASN.1 for UL RTOA Measurement | Huawei, CATT, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-226121 | Correction on Resource configuration for IAB | Huawei, Lenovo, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-226122 | Correction on definition of Multicast F1-U Context | CATT |
| R3-226123 | R17 Correction on SHR report to TS38.423 | ZTE, CATT, Samsung, CMCC |
| R3-226124 | R16 Correction on RACH report to TS38.423 | ZTE, CATT, Samsung, CMCC |
| R3-226125 | R17 Correction on RACH report to TS38.423 | ZTE, CATT, Samsung, CMCC |
| R3-226126 | Provision of MBS Multicast F1-U references to UE Context in gNB-CU enabling retrieval of data forwarding progress information | Ericsson, AT&T, Nokia, Nokia Shanghai Bell, Qualcomm, Lenovo |
| R3-226127 | Correction on generation of gap type over F1 in Rel-16 | ZTE, China Telecom, Lenovo, China Unicom, Ericsson |
| R3-226128 | Correction on generation of gap type over F1 in Rel-17 | ZTE, China Telecom, Lenovo, China Unicom, Ericsson |
| R3-226129 | Correction on Multicast Mobility procedure | Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo, Samsung |
| R3-226130 | R16CR for DAPS over F1 to TS38.473 | ZTE, Ericsson, CATT, Google, Samsung, Intel Corporation, Lenovo, NEC |
| R3-226131 | R17CR for DAPS over F1 to TS38.473 | ZTE, Ericsson, CATT, Google, Samsung, Intel Corporation, Lenovo, NEC |
| R3-226132 | Correction of TRP TEG | Nokia, Nokia Shanghai Bell, Ericsson, CATT |
| R3-226133 | Correction of TRP TEG | Nokia, Nokia Shanghai Bell, Ericsson, CATT |
| R3-226134 | Correction on non-MBS-supporting to MBS-supporting handover on TS 37.483 | CATT, Nokia, Nokia Shanghai Bell |
| R3-226135 | Correction to 38.470 on Positioning System Information | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| R3-226136 | Correction to 38.470 on Positioning System Information | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| R3-226137 | Introduction of further multicast session flow on MRB type reconfiguration | Ericsson, AT&T, Nokia, Nokia Shanghai Bell |
| R3-226138 | Correction to TS 38.423 on RRC transfer | ZTE |
| R3-226139 | PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | NEC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Intel Corporation, Rakuten Mobile Inc, Samsung, Huawei |
| R3-226140 | PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | NEC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Intel Corporation, Rakuten Mobile Inc, Samsung, Huawei |
| R3-226141 | Correction to the PRS Measurement configuration procedures | Ericsson |
| R3-226142 | Correction on Multicast Session Establishment | Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo, Ericsson, Google |
| R3-226143 | Correction on positioning SI delivery over F1AP | Huawei, China Unicom, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| R3-226144 | Correction on positioning SI delivery over F1AP | Huawei, China Unicom, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| R3-226145 | The inclusion of the CCO Issue Detection over Xn signalling | Samsung, Verizon, Ericsson, ZTE |
| R3-226146 | Resource Status Reporting correction | Ericsson |
| R3-226147 | Clarification on initialRXDELIV over E1AP | Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, CATT |
| R3-226148 | Correction on User Inactivity for Multicast Session | Lenovo, Huawei, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-226149 | Correction on F1-U tunnels for multicast MRB | Lenovo, Huawei, Nokia, Nokia Shanghai Bell |
| R3-226150 | draftCR to TS 38.300 on IAB-topology definition | Qualcomm Inc. |
| R3-226151 | Correction to IoT NTN about constructing the Mapped Cell ID | CATT, Ericsson, ZTE, Nokia, Huawei |
| R3-226152 | Correction on NSAG | ZTE, Nokia, Nokia Shanghai Bell, CATT, Samsung, Qualcomm Incorporated, Ericsson, LG Electronics, Huawei |
| R3-226153 | NSAG for cell reselection and random access | Huawei, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Samsung, CATT, Qualcomm Incorporated, LG Electronics |
| R3-226154 | Minimization of data loss and duplication avoidance during mobility from MBS non upporting gNB to supporting gNB | Huawei, CBN, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Lenovo |
| R3-226155 | Corrections on NRPPa functions and procedures | CATT |
| R3-226156 | draft CR to 38.300 on RAN visible QoE | ZTE |
| R3-226157 | Failure handling for SCG MRO | Nokia, Nokia Shanghai Bell, CATT |
| R3-226158 | Correction of UE History Information for CHO | Samsung, ZTE, Ericsson |
| R3-226159 | Correction for TS 37.340 on UHI MR-DC | ZTE, Samsung, Lenovo, China Telecom, Ericsson |
| R3-226160 | SHR correction | Huawei, Qualcomm, Deutsche Telekom , CMCC, China Unicom, Vodafone, BT |
| R3-226772 | R17 Correction on SHR report to TS38.423 | ZTE, CATT, Samsung, CMCC |
| R3-226773 | Correction on RACH report | ZTE, CATT, Samsung, CMCC |
| R3-226792 | Correction to IoT NTN about constructing the Mapped Cell ID | CATT, Ericsson, ZTE, Nokia, Huawei |
| R3-226794 | Provision of MBS Multicast F1-U references to UE Context in gNB-CU enabling retrieval of data forwarding progress information | Ericsson, AT&T, Nokia, Nokia Shanghai Bell, Qualcomm, Lenovo |
| 10.1 | General | |
| R3-226103 | BLCR to 38.300:enhancement of SON | CMCC |
| R3-226108 | (BLCR to 38.423) Addition of SON features enhancement | Samsung |
| R3-226714 | Update of work Plan for Enhancement of Data Collection for SON_MDT in NR standalone and MR-DC WI | CMCC |
| R3-226927 | (BLCR to 38.423) Addition of SON features enhancement | Samsung |
| R3-226928 | (BLCR to 38.473) Addition of SON features enhancement | Huawei |
| 10.2.1 | SHR and SPCR | |
| R3-226262 | SHR and SPCR | Huawei |
| R3-226278 | Discussion on SON enhancement for SHR and SPCR | CATT |
| R3-226418 | SON enhancements for SPCR and inter-RAT SHR | Lenovo |
| R3-226479 | Inter-RAT SHR and SPR discussion | Ericsson |
| R3-226513 | Inter-RAT Successful Handover Report and Successful PSCell Change Report | Qualcomm Incorporated |
| R3-226564 | Discussion on inter-RAT SHR and SPCR | ZTE |
| R3-226585 | SON enhancement for Successful Handover Report and Successful PSCell Change Report | Samsung |
| R3-226716 | SHR for intra-system inter-RAT handover | CMCC |
| R3-226803 | CB: # 17_SHR_SPCR - Summary of email discussion | ZTE - moderator |
| 10.2.2 | MRO | |
| R3-226201 | Further consideration on the CPC Execution to wrong PSCell | Nokia, Nokia Shanghai Bell |
| R3-226202 | [TP to TS38423, SON] SN support for MRO for fast MCG recovery | Nokia, Nokia Shanghai Bell |
| R3-226263 | (TPs for SON BLCRs for TS 36.300): MRO related objectives | Huawei |
| R3-226279 | Discussion on MRO for CPAC and SCG failure | CATT |
| R3-226280 | Discussion on MRO for voicefallback and fastMCGrecovery | CATT |
| R3-226419 | (TP for SON BLCR for 36.300) MRO for fast MCG link recovery and SCG failure | Lenovo |
| R3-226420 | (TP for SON BLCR for 38.300) MRO for inter-system handover for voice fallback | Lenovo |
| R3-226421 | (TP for SON BLCR for 37.340) SON enhancements for CPAC | Lenovo |
| R3-226422 | Update of WF on the MRO scenarios | Lenovo |
| R3-226473 | Further discussion on MRO enhancements in Rel-18 | ZTE |
| R3-226474 | (TP for BL CRs 36.300, 36.423 and 38.300) MRO enhancements on SCG failure in (NG)EN-DC and inter-system HO for voice fallback | ZTE, China Unicom |
| R3-226480 | SON enhancements for Mobility Robustness | Ericsson |
| R3-226514 | MRO enhancements for CPAC, fast MCG recovery and MR-DC SCG failures | Qualcomm Incorporated |
| R3-226586 | SON enhancements for CPAC and MCG failure recovery | Samsung |
| R3-226587 | Discussion on MR-DC SCG failure and inter-RAT CPAC | Samsung |
| R3-226755 | (TPs for SON BLCRs for TS 36.300): MRO related objectives | Huawei |
| R3-226804 | CB: # 18_MRO - Summary of email discussion | Huawei - moderator |
| 10.2.3 | RACH Enhancements | |
| R3-226281 | Discussion on RACH enhancement | CATT |
| R3-226300 | (TPs for SON BLCRs for TS 38.473 and TS 38.423): RACH optimisation | Huawei |
| R3-226481 | (TP for SON BL CR for TS 38.423) RACH Optimization enhancement | Ericsson |
| R3-226515 | RACH optimization enhancements | Qualcomm Incorporated |
| R3-226530 | On network method for RACH report retrieval | Nokia, Nokia Shanghai Bell |
| R3-226565 | Initial consideration on RACH enhancement | ZTE |
| R3-226575 | Discussion on SON for RACH | Samsung |
| R3-226665 | RA report enhancement about RACH partitioning | Intel Corporation |
| R3-226715 | SON for RACH optimization | CMCC |
| R3-226805 | CB: #19_RACH - Summary of email discussion | Qualcomm - moderator |
| R3-226858 | (TP for SON BL CR for TS 38.423) RACH Optimization enhancement | Ericsson |
| R3-226881 | (TPs for SON BLCRs for TS 38.473 and TS 38.423): RACH optimisation | Huawei |
| R3-226911 | (TP for SON BL CR for TS 38.473) RACH Optimization enhancement | Ericsson |
| R3-226912 | (TP for SON BLCR for TS 38.423): RACH optimisation | Huawei |
| 10.2.4 | SON/MDT Enhancements for Non-Public Networks | |
| R3-226282 | Discussion on SON enhancement for NPN | CATT |
| R3-226301 | (TP for MDT BLCR for TS 38.413): SON/MDT for NPN | Huawei |
| R3-226482 | SON enhancements for Non-public networks | Ericsson |
| R3-226516 | SON MDT enhancements for Non-Public networks | Qualcomm Incorporated |
| R3-226531 | On open points for SON/MDT enhancements for NPN | Nokia, Nokia Shanghai Bell |
| R3-226566 | Discussion on MDT support in NPN and TPs | ZTE |
| R3-226576 | Discussion on SON for NPN | Samsung |
| R3-226666 | MDT enhancements for NPN | Intel Corporation |
| R3-226667 | Text Proposal for TS 38.413 on area scope for NPN | Intel Corporation |
| R3-226808 | CB: # 20_NPNSupport - Summary of email discussion | Ericsson - moderator |
| R3-226883 | (TP for SON BL CR for TS 38.423) Addition of PNI-NPN in MDT Area Scope | Ericsson |
| R3-226893 | (TP for MDT BLCR for TS 38.413): SON/MDT for NPN | Huawei |
| R3-226902 | (TP for SON BL CR for TS 38.413) Addition of PNI-NPN in MDT Area Scope | Ericsson |
| 10.2.5 | SON for NR-U | |
| R3-226187 | LS on Possibility on LBT-FailureRecoveryConfig | RAN2 |
| R3-226194 | The LBT waiting time for correct NR-U MRO analysis | Nokia, Nokia Shanghai Bell |
| R3-226283 | Discussion on SON enhancement for NR-U | CATT |
| R3-226302 | (TPs for SON BLCR for TS 38.423):SON for NR-U | Huawei |
| R3-226387 | Retrieval of LBT config for NR-U MRO (incl. draft response LS) | Nokia, Nokia Shanghai Bell |
| R3-226423 | Discussion on MRO for NR-U | Lenovo |
| R3-226475 | Further discussion on NR-U optimizations in Rel-18 | ZTE |
| R3-226483 | [Draft] LS Reply to Possibility on LBT-FailureRecoveryConfig | Ericsson |
| R3-226484 | NR-U enhancements for MRO and MLB | Ericsson |
| R3-226485 | (TP for SON BL CR for TS 38.423, TS 38.473) Radio Resource Status per NR-U Channel | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Deutsche Telekom |
| R3-226487 | (TP for SON BL CR for TS 38.423) Channel Occupancy of second tier neighbors | Ericsson, Qualcomm Incorporated, Deutsche Telekom |
| R3-226517 | SON enhancements for NR-U | Qualcomm Incorporated |
| R3-226577 | Discussion on SON for NR-U | Samsung |
| R3-226668 | NR-U enhancements for MLB and MRO | Intel Corporation |
| R3-226809 | Reply LS to RAN2 | Nokia |
| 10.2.6 | MDT Enhancements | |
| R3-226403 | Signalling based immediate MDT in NR-DC | Huawei |
| R3-226486 | RAN3’s position on the network-based on the support of signalling based logged MDT configuration override protection in Rel-18 | Ericsson |
| 11.1 | General | |
| R3-226109 | (BLCR to 38.401) Enhancement on NR QoE | Samsung |
| R3-226110 | (BLCR to 38.473) Enhancement on NR QoE | ZTE |
| R3-226760 | Update Workplan for Rel-18 NR QoE Enhancement | China Unicom |
| 11.2 | Support for New Service Type and RRC_INACTIVE/RRC_IDLE states | |
| R3-226208 | Handling of MBS QMC context in idle mode | Nokia, Nokia Shanghai Bell |
| R3-226209 | Discussion on high mobility scenarios | Nokia, Nokia Shanghai Bell |
| R3-226425 | QoE for RRC_INACTIVE/RRC_IDLE states | Lenovo |
| R3-226426 | (TP to 38.423 & 38.420) Support of QoE measurement in RRC_INACTIVE | Lenovo |
| R3-226463 | QoE and RVQoE Measurement Support for MBS | Ericsson |
| R3-226464 | QMC Support for High Mobility Scenarios | Ericsson |
| R3-226518 | QMC in RRC_INACTIVE and RRC_IDLE for MBS | Qualcomm Incorporated |
| R3-226519 | QoE enhancements for high mobility scenarios | Qualcomm Incorporated |
| R3-226554 | Discussion on NR QoE in RRC_INACTIVE/RRC_IDLE states | CATT |
| R3-226592 | Further discussion on QMC for MBS and RRC state | Samsung |
| R3-226606 | Further discussions on the support of MBS QoE | Huawei |
| R3-226608 | (TP for NR_QoE BLCR for 38.300) on QoE measurement enhancements | Huawei |
| R3-226702 | Consideration for QMC in RRC_IDLE and RRC_INACTIVE | CMCC |
| R3-226725 | Discussion on QoE configuration in RRC_INACTIVE RRC_IDLE states | Xiaomi |
| R3-226747 | [Draft] LS to RAN2 on MBS QoE | ZTE |
| R3-226748 | Discussion on INACTIVE IDLE QoE and high speed scenario | ZTE |
| R3-226761 | Discussion on QoE measurement in RRC_INACTIVE and RRC_IDLE states | China Unicom |
| R3-226844 | CB: # 36_InactiveQoE - Summary of email discussion | ZTE - moderator |
| R3-226890 | LS to SA4 on id of MBS session in MBS QoE configuration | ZTE |
| R3-226916 | LS to SA4 on id of MBS session in MBS QoE configuration | ZTE |
| 11.3 | Support QoE for NR-DC | |
| R3-226210 | Cost/benefit of m-based QMC configuration in the SN | Nokia, Nokia Shanghai Bell |
| R3-226211 | Discussion on RVQoE reports for DC | Nokia, Nokia Shanghai Bell |
| R3-226427 | QoE measurement in NR-DC | Lenovo |
| R3-226428 | (TP to TS 38.420&423) Support of QoE measurement in NR-DC | Lenovo |
| R3-226465 | The Support for QoE and RVQoE Measurements and Reporting in NR-DC Scenarios | Ericsson |
| R3-226520 | Support for QoE in NR-DC | Qualcomm Incorporated |
| R3-226521 | MDT-QoE alignment and QoE measurement continuity in mobility scenarios in NR-DC | Qualcomm Incorporated |
| R3-226555 | Discussion on Support for legacy QoE in NR-DC | CATT |
| R3-226556 | (TP to BLCR for TS38.423) Support for legacy QoE in NR-DC | CATT |
| R3-226557 | Discussion on Support for RV-QoE in NR-DC | CATT |
| R3-226593 | Further discussion on support of NR-DC | Samsung |
| R3-226607 | Further discussions on the support for QoE in NR-DC | Huawei |
| R3-226609 | (TP for NR_QoE BLCR for 37.340) on QoE measurement in NR-DC | Huawei |
| R3-226719 | Discussion on QoE configuration and reporting in NR-DC | ZTE |
| R3-226720 | Discussion on MDT alignment and Mobility in NR-DC | ZTE |
| R3-226726 | Discussion on QoE in NR-DC | Xiaomi |
| R3-226727 | (Draft CR for TS 38.300) Introduction of QoE configuration in NR-DC | Xiaomi |
| R3-226762 | Discussion on QoE measurement in NR-DC | China Unicom |
| R3-226846 | CB: # 37_NR-DCQoE - Summary of email discussion | Huawei - moderator |
| 11.4 | Left-over from R17 | |
| R3-226466 | Enhancements of RAN Visible QoE Measurements and Reporting | Ericsson |
| R3-226467 | On the OAM-set Priorities for QoE Reporting | Ericsson |
| R3-226522 | Enhancements to RAN visible QoE | Qualcomm Incorporated |
| R3-226558 | Discussion on Left-over issues | CATT |
| R3-226626 | Further discussion on the support of R17 left-over features | Huawei |
| R3-226721 | Discussion on R17 QoE left-over issues | ZTE |
| R3-226728 | Discussion on RVQoE | Xiaomi |
| R3-226763 | Further discussion on R17 leftover issues | China Unicom |
| R3-226847 | CB: # 38_LefrOverQoE - Summary of email discussion | Ericsson - moderator |
| 12.1 | General | |
| R3-226105 | CR to 38.401 for addition of AIML-RAN feature in the case of split architecture | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Samsung, Intel Corporation, CMCCrporation, CMCC |
| R3-226107 | Draft CR to 38.300 on AI/ML for NG-RAN | CMCC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, CATT, Samsung, Lenovo, Intel Corporation |
| R3-226195 | Draft CR to 38.300 on AI/ML for NG-RAN | China Mobile (Hangzhou) Inf. |
| R3-226932 | (BLCR to 38.423) for AI/ML for NG-RAN | Ericsson |
| 12.2.1 | Stage2 Related | |
| R3-226578 | Discussion on Stage 2 impact of AI/ML for NG-RAN | Samsung |
| R3-226598 | Open issues related to Stage 2 | LG Electronics Inc. |
| R3-226610 | (TP for AI&ML BLCR for TS38.300) Further discussions on common issues and stage 2 updates on the introduction of RAN AI/ML | Huawei |
| R3-226660 | Discussion on New Procedure for AI/ML Information | Intel Corporation |
| R3-226740 | Discussion on stage2 impacts for AIRAN feature | ZTE |
| R3-226741 | TP to 38.300 for the stage2 impacts on AIML procedure | ZTE |
| R3-226810 | CB: # 22_Stage2 - Summary of email discussion | ZTE - moderator |
| R3-226884 | CB: # 22_Stage2 - Summary of email discussion | ZTE - moderator |
| 12.2.2.1 | Xn interface | |
| R3-226274 | Discussion on Mobility Optimization Outputs | InterDigital |
| R3-226275 | (TP for AIML BLCR for TS 38.423) Mobility Optimization Outputs | InterDigital |
| R3-226276 | Validity Time Discussion | InterDigital |
| R3-226277 | (TP for AIML BLCR for TS 38.423) QoS Feedback | InterDigital |
| R3-226364 | Discussion on XnAP impacts of non-UE-associated metrics | CATT |
| R3-226365 | Discussion on XnAP impacts of AI/ML for UE associated metrics | CATT |
| R3-226366 | TP on TS 38.420 for AI/ML | CATT |
| R3-226367 | TP on TS 38.423 for AI/ML | CATT |
| R3-226376 | AIML Energy Saving | NEC |
| R3-226377 | AIML Load balancing | NEC |
| R3-226378 | Predicated resource status information in AI/ML energy saving | NEC |
| R3-226388 | Further discussion on open issues for NG-RAN AI/ML | NTT DOCOMO, INC. |
| R3-226429 | Discussion on time information in prediction request | Lenovo |
| R3-226430 | Discussion on issues related to prediction accuracy | Lenovo |
| R3-226431 | Discussion on prediction and feedback transfer during handover | Lenovo |
| R3-226432 | Miscellaneous Xn interface issues | Lenovo |
| R3-226495 | (TP for AI/ML BLCR to TS38.423) Procedures for exchanging AI/ML-related information | Ericsson |
| R3-226496 | AI/ML capability discovery | Ericsson |
| R3-226498 | AI/ML Network Energy Saving | Ericsson |
| R3-226499 | Cell Trajectory Prediction exchange | Ericsson, Inter Digital, Verizon Wireless |
| R3-226500 | Feedback for AIML | Ericsson |
| R3-226507 | Open points on validity time and prediction accuracy | Ericsson |
| R3-226508 | Cell trajectory prediction over Xn | Ericsson, Inter Digital, Verizon Wireless |
| R3-226538 | (TP for TS 38.423) AI/ML Related Information and Procedures in Xn | Nokia, Nokia Shanghai Bell |
| R3-226539 | AI/ML Energy Saving Open Aspects | Nokia, Nokia Shanghai Bell |
| R3-226540 | (TP for TS 38.423) Cell-based UE Trajectory Prediction | Nokia, Nokia Shanghai Bell |
| R3-226541 | AI/ML Feedback Configuration | Nokia, Nokia Shanghai Bell |
| R3-226579 | Discussion on Xn impact of AI/ML for NG-RAN | Samsung |
| R3-226581 | TP for energy efficiency exchange for AI/ML for NG-RAN | Samsung |
| R3-226582 | TP for predicted resource status reporting procedure for AI/ML for NG-RAN | Samsung |
| R3-226583 | TP for predicted UE trajectory exchange for AI/ML for NG-RAN | Samsung |
| R3-226599 | Open issues related to Xn interface | LG Electronics Inc. |
| R3-226611 | (TP for AI&ML BLCR for 38.423) Further discussions on remaining open issues for energy saving using AI/ML | Huawei |
| R3-226612 | Further discussions on remaining open issues for mobility enhancements using AI/ML | Huawei |
| R3-226613 | Further discussions on remaining open issues for load balancing using AI/ML | Huawei |
| R3-226642 | XN enhancements for NG-RAN AI/ML | Qualcomm India Pvt Ltd |
| R3-226647 | Signaling support for AI/ML information | AT&T |
| R3-226661 | Discussion on Stage 3 of Procedure Enhancement for AI/ML Information | Intel Corporation |
| R3-226662 | Discussion on mobility optimization and UE trajectory prediction | Intel Corporation |
| R3-226663 | Discussion on Validity Time and Confidence Level of Predicted Information | Intel Corporation |
| R3-226709 | On the Xn procedures of AI/ML for NG-RAN | CMCC |
| R3-226710 | Remaining issues on predicted information | CMCC |
| R3-226711 | Discussion on event-based reporting | CMCC |
| R3-226713 | Open Issues on AI/ML for NG-RAN Energy Saving | CMCC |
| R3-226742 | Discussion on the stage3 standard impacts of AIRAN | ZTE |
| R3-226743 | TP to 38.423 and 38.420 for unified AI-ML procedures | ZTE |
| R3-226753 | Discussion on the new procedure of AI/ML information exchange | China Telecommunications |
| R3-226811 | CB: # 23_LBProcedure - Summary of email discussion | Samsung - moderator |
| R3-226812 | CB: # 24_ESProcedures - Summary of email discussion | CATT - moderator |
| R3-226813 | CB: # 25_MEProcedure - Summary of email discussion | Interdigital - moderator |
| R3-226869 | TP to TS 38.423 for predicted resource status reporting procedure for AI/ML for NG-RAN | Samsung |
| R3-226900 | Cell trajectory prediction over Xn | Ericsson, InterDigital, Verizon Wireless, Qualcomm Incorporated |
| R3-226931 | TP to TS 38.423 for the procedure used for reporting of AI/ML related information for NG-RAN | Samsung, ZTE, CMCC, Nokia, Nokia Shanghai Bell, Ericsson, Intel Corporation, Huawei, Lenovo, CATT |
| R3-226933 | TP to TS 38.423 for the procedure used for reporting of AI/ML related information for NG-RAN | Samsung, ZTE, CMCC, Nokia, Nokia Shanghai Bell, Ericsson, Intel Corporation, Huawei, Lenovo, CATT |
| 12.2.2.2 | Other interfaces | |
| R3-226368 | Discussion on E1AP and F1AP impacts of non-UE-associated metrics | CATT |
| R3-226369 | Discussion on E1AP and F1AP impacts of UE-associated metrics | CATT |
| R3-226433 | (TP for TS37.483 TS37.480) Support UE traffic prediction over E1 interface | Lenovo |
| R3-226615 | CR to 38.473 On the introduction of RAN AI/ML | Huawei |
| R3-226756 | Discussion on the Support of AI/ML over F1 and E1 interface | China Telecommunications |
| 12.3 | Others | |
| R3-226434 | Discussion on transferring visited cell list to old NG-RAN node | Lenovo |
| R3-226497 | (TP for AI/ML BLCT to TS38.423 and TS38.413) MDT Enhancements for AI/ML | Ericsson, Deutsche Telekom |
| R3-226542 | (TP for TS 38.413) MDT Enhancements for NG-RAN AI/ML | Nokia, Nokia Shanghai Bell |
| R3-226543 | [Draft] LS on MDT Enhancements for AI/ML for NG-RAN | Nokia, Nokia Shanghai Bell |
| R3-226580 | Discussion on MDT enhancement for AI/ML for NG-RAN | Samsung |
| R3-226614 | Further discussions on the need of MDT enhancements | Huawei |
| R3-226646 | MDT Enhancements for NG-RAN AI/ML | Qualcomm Incorporated |
| R3-226664 | Discussion on MDT enhancement | Intel Corporation |
| R3-226712 | Discussion on MDT Enhancements | CMCC |
| R3-226744 | Discussion on MDT enhancement for continuous AI-ML related information | ZTE |
| R3-226745 | [DRAFT] LS on the MDT enhancement to support continuous AI-ML related information reporting from UE | ZTE |
| 13.1 | General | |
| R3-226186 | Reply LS on FS_VMR solutions review | RAN2 |
| R3-226267 | Workplan for Rel-18 mobile IAB | Qualcomm Inc. (Rapporteur) |
| 13.2 | Support IAB-node mobility | |
| R3-226268 | Topology adaptation for mobile IAB | Qualcomm Inc. |
| R3-226271 | Discussion on the DU Migration of Mobile IAB-node | CANON Research Centre France |
| R3-226309 | Discussion on IAB-DU consecutive partial migration and full migration | Nokia, Nokia Shanghai Bell |
| R3-226310 | Support for mobile IAB | Nokia, Nokia Shanghai Bell |
| R3-226327 | Discussion on IAB-node consecutive partial migrations | Fujitsu |
| R3-226328 | Discussion on IAB full migration | Fujitsu |
| R3-226350 | (TP for NR_mobile_IAB BL CR for TS 38.401):Partial migration for mobile IAB | Huawei |
| R3-226351 | DU migration for mobile IAB | Huawei |
| R3-226382 | Discussion on inter-donor migration in mobile IAB scenario | ZTE |
| R3-226414 | Migration Procedure for Mobile IAB-Nodes | Ericsson |
| R3-226435 | Discussion on mobile IAB-node inter-donor topology adaptation | Lenovo |
| R3-226436 | Inter-donor full migration procedure of mobile IAB | Lenovo |
| R3-226603 | Discussion on IAB-node mobility | Samsung |
| R3-226730 | Discussion on IAB-node mobility | Xiaomi |
| R3-226826 | CB: # 35_IAB1_Mobility- Summary of email discussion | Qualcomm - moderator |
| 13.3 | Mobility Enhancements | |
| R3-226269 | Enhancements for mobility of IAB-node and its served UEs | Qualcomm Inc. |
| R3-226311 | Discussion on mobility enhancements | Nokia, Nokia Shanghai Bell |
| R3-226329 | Discussion on IAB-node mobility together with served UEs | Fujitsu |
| R3-226352 | (TP for NR_mobile_IAB BL CR for TS 38.423): Mobility enhancement for mobile IAB | Huawei |
| R3-226383 | Discussion on enhancements to UE migration in mobile IAB scenario | ZTE |
| R3-226384 | Discussion on mobility enhancement for mobile IAB | ZTE |
| R3-226407 | Discussion on mobility enhancements for mobile-IAB | KT Corp. |
| R3-226415 | Enhancements of IAB-Node Mobility | Ericsson |
| R3-226437 | Mobility enhancements for mobile IAB-node and its served UE | Lenovo |
| R3-226604 | Discussion on mobility enhancements | Samsung |
| R3-226731 | Discussion on mobility enhancement | Xiaomi |
| R3-226831 | LS on static and dynamic TAC solutions for mobile IAB node | ZTE |
| 13.4 | Mitigation of interference | |
| R3-226312 | Mobile IAB interference mitigation | Nokia, Nokia Shanghai Bell |
| R3-226353 | PCI collision for mobile IAB | Huawei |
| R3-226385 | Discussion on PCI collision avoidance for mobile IAB | ZTE |
| R3-226416 | PCI Collision Avoidance for Mobile IAB-Nodes | Ericsson |
| R3-226438 | Interference mitigation of mobile IAB-node mobility | Lenovo |
| R3-226605 | Discussion on mitigation of interference | Samsung |
| R3-226732 | Discussion on mitigation of interference | Xiaomi |
| 14.1 | General | |
| R3-226104 | Introduction of L1/L2 inter-cell mobility | Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-226930 | Introduction of L1/L2 inter-cell mobility | Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
| 14.2 | Signaling Support for L1/L2 based Inter-Cell Mobility | |
| R3-226176 | LS on L1 intra- and inter- frequency measurement and configurations for L1/L2-based inter-cell mobility | RAN1 |
| R3-226185 | LS on RAN2 agreements about L1/L2-triggered mobility (LTM) | RAN2 |
| R3-226196 | TP (BL CR TS 38.401) Intra-gNB-DU L1/2 Triggered Mobility (LTM) Procedure | Nokia, Nokia Shanghai Bell |
| R3-226197 | Discussion on Additional Considerations for L1/2 Triggered Mobility (LTM) | Nokia, Nokia Shanghai Bell |
| R3-226227 | Additions for L1/L2 based inter-cell mobility | Ericsson, Huawei |
| R3-226230 | Solutions for L1/L2 based inter-cell mobility | Ericsson |
| R3-226257 | (TP for L1L2Mob BLCR for TS 38.401): Inter-DU L1/L2 Mobility procedure | Huawei, Ericsson |
| R3-226258 | (TP for L1L2Mob BLCR for TS 38.401): L1/L2 Inter-cell Mobility | Huawei |
| R3-226330 | Collision between L1/L2-triggered mobility and L3 mobility | vivo |
| R3-226331 | Discussion on L1/L2-triggered mobility | vivo |
| R3-226372 | Support for L1/L2 based inter-cell mobility | NEC |
| R3-226389 | Discussion on L1/L2 based Inter-Cell Mobility | China Telecommunication |
| R3-226439 | Discussion on L1L2 based inter-cell mobility | Lenovo |
| R3-226440 | (TP to TS 38.401 & TS 38.470) Support of L1L2 based inter-cell mobility | Lenovo |
| R3-226527 | Data forwarding in LTM | Qualcomm Incorporated |
| R3-226529 | Signalling Support for L1/L2 based Inter-Cell Mobility | Qualcomm Incorporated |
| R3-226600 | Open issues for L1/L2 based inter-cell mobility | LG Electronics Inc. |
| R3-226601 | (TP for NR_Mob_enh2 BL CR for TS 38.401) Open issues for L1/L2 based inter-cell mobility | LG Electronics Inc. |
| R3-226602 | (TP for NR_Mob_enh2 BL CR for TS 38.473) Open issues for L1/L2 based inter-cell mobility | LG Electronics Inc. |
| R3-226636 | TP for LTM BL CR to TS 38.401 and 38.473 | ZTE |
| R3-226637 | [DRAFT] Reply LS on L1 intra- and inter- frequency measurement and configurations for L1/L2-based inter-cell mobility | ZTE |
| R3-226674 | General principles for L1/L2 based inter-cell mobility | Intel Corporation |
| R3-226675 | Discussions for L1/L2 based "intra-DU" mobility (including TPs for L1/L2 Mob for TS 38.401 and TS 38.473) | Intel Corporation |
| R3-226676 | Discussions on L1/L2 based "intra-CU inter-DU" mobility (including TPs for L1/L2 Mob for TS 38.401 and TS 38.473) | Intel Corporation |
| R3-226688 | Discussion of L1/L2 based Inter-Cell Mobility | NTT DOCOMO INC. |
| R3-226692 | (TP for L1L2 Mob BLCR for TS 38.401) Discussion about the open issues for L1L2 mobility | CATT |
| R3-226693 | Discussion on L1 measurement and TCI states transfer for inter-DU case | CATT, Fujitsu |
| R3-226694 | [Draft] Reply LS for L1L2-based inter-cell mobility | CATT, Fujitsu |
| R3-226696 | Discussion on L1/L2 based Inter-cell Mobility | Samsung |
| R3-226703 | Discussion on L1/L2 based Inter-Cell Mobility | CMCC |
| R3-226828 | CB: # 30_MobilityEhn -L1L2mobility - Summary of email discussion | Huawei - moderator |
| R3-226829 | Reply LS on L1 intra- and inter- frequency measurement and configurations for L1/L2-based inter-cell mobility | ZTE |
| R3-226852 | (TP for L1L2Mob BLCR for TS 38.401): Inter-DU L1/L2 Mobility procedure | Huawei, Ericsson |
| R3-226868 | Additions for L1/L2 based inter-cell mobility | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Intel Corporation |
| R3-226913 | (TP for L1L2Mob BLCR for TS 38.401): Inter-DU L1/L2 Mobility procedure | Huawei, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Intel Corporation |
| 14.3 | Support CHO in NR-DC | |
| R3-226192 | [TP to TS38423, CHO with NRDC] Data forwarding enhancements for CHO with SCG(s) kept at the target side | Nokia, Nokia Shanghai Bell |
| R3-226231 | CHO with target SCG(s) | Ericsson |
| R3-226248 | (TP for CHO with NR-DC to TS 37.340): Early data forwarding optimization for CHO with SCG procedure | ZTE |
| R3-226323 | (TP to CHO BL CR of 37.340) Consideration on CHO Related aspects | Huawei |
| R3-226390 | Discussion on CHO in NR-DC | China Telecommunication |
| R3-226441 | Discussion on CHO in NR-DC | Lenovo |
| R3-226526 | CHO including target MCG and candidate SCGs | Qualcomm Incorporated |
| R3-226559 | Discussion on CHO with SCG and multiple SCGs | CATT |
| R3-226677 | Discussions on optimizing duplicated early data forwarding in CHO with SCG(s) | Intel Corporation |
| R3-226876 | CB: # 32_MobilityEnh_CHO - Summary of email discussion | ZTE-moderator |
| 14.4 | Others | |
| R3-226193 | Source-node- and UPF-based data forwarding | Nokia, Nokia Shanghai Bell |
| R3-226232 | NR-DC with Selective Activation | Ericsson |
| R3-226249 | (TP for Selective activation to TS 38.423): Support of Selective activation | ZTE |
| R3-226324 | (TP to TS 38.423 BL CR) Consideration on selective activation of SCGs | Huawei |
| R3-226332 | Transfer Information of Configured CPC to Target SN | vivo |
| R3-226373 | Selective Activation of the cell groups | NEC |
| R3-226391 | Discussion on selective activation of cell groups | China Telecommunication |
| R3-226442 | (TP for TS 38.473) On SCG selective activation | Lenovo |
| R3-226528 | Selective activation of cell groups in NR-DC | Qualcomm Incorporated |
| R3-226560 | Discussion on NR-DC with selective activation of the cell groups | CATT |
| R3-226689 | Discussion of selective activation | NTT DOCOMO INC. |
| R3-226695 | Considerations on selective activation of the cell groups | Samsung |
| 15.1 | General | |
| R3-226172 | LS on re-establishment of the MBS context during mobility registration update or service request procedure | SA2 |
| R3-226179 | Reply LS on FS_5MBS_Ph2 progress | RAN2 |
| R3-226362 | Discussion on re-establishment of the MBS context during mobility registration update or service request procedure | CATT |
| R3-226363 | [Draft]Reply LS on the re-establishment of the MBS context during mobility registration update or service request procedure | CATT |
| R3-226910 | Reply LS on the re-establishment of the MBS context during mobility registration update or service request procedure | CATT |
| R3-226922 | Reply LS on the re-establishment of the MBS context during mobility registration update or service request procedure | CATT |
| 15.2 | Support for MBS reception in RAN sharing scenarios | |
| R3-226203 | Support of MBS in RAN sharing scenarios | Qualcomm Incorporated |
| R3-226206 | Broadcast reception in a certain area | TD Tech, Chengdu TD Tech |
| R3-226207 | Sharing processing for both unicast reception and broadcast reception | Chengdu TD Tech, TD Tech |
| R3-226321 | (TPs to TS 38.300, TS 38.413 BL CRs) MBS reception in RAN sharing scenario | Huawei, CBN |
| R3-226360 | Discussion on efficient MBS reception in RAN sharing scenario | CATT, CBN, China Telecom |
| R3-226381 | MBS RAN sharing scenario | NEC |
| R3-226454 | Support of resource efficiency for MBS reception in RAN sharing scenarios - further discussion | Ericsson |
| R3-226491 | (TP for TS 38.300) RAN Impacts of Rel-18 RAN Sharing Solutions | Nokia, Nokia Shanghai Bell |
| R3-226596 | Discussion on MBS RAN sharing | Samsung |
| R3-226704 | Discussion on MBS reception in RAN sharing scenarios | CMCC |
| R3-226738 | Native or foreign TMGI - a backward compatibility perspective | ZTE |
| R3-226848 | CB: #40_SharingMBS - Summary of email discussion | Huawei - moderator |
| 15.3 | Support for RRC_INACTIVE state | |
| R3-226204 | Enhancements to support Multicast reception by UEs in RRC_INACTIVE state | Qualcomm Incorporated |
| R3-226205 | Multicast reception in RRC_INACTIVE state | TD Tech, Chengdu TD Tech |
| R3-226322 | (TP to TS 38.300, TS 38.401 BL CRs) Multicast Reception for RRC_INACTIVE state Ues | Huawei, CBN |
| R3-226361 | Discussion on multicast over RRC INACTIVE | CATT |
| R3-226379 | MBS Inactive Reception | NEC |
| R3-226380 | (TP for NR-MBS-Enh to TS38.473 BLCR) Indication to DU that the RRC_INACTIVE UE is interested in MBS session | NEC |
| R3-226443 | Multicast reception in RRC_INACTIVE | Lenovo |
| R3-226455 | Support of multicast reception by UEs in RRC_INACTIVE state - further discussion | Ericsson |
| R3-226492 | (TP for TS 38.300) Assistance Information needed at gNB to enable multicast reception in RRC inactive | Nokia, Nokia Shanghai Bell |
| R3-226597 | Discussion on MC support for RRC Inactive | Samsung |
| R3-226705 | Multicast Reception in RRC_INACTIVE state | CMCC |
| R3-226739 | Multicast reception in RRC_INACTIVE | ZTE |
| 16.1 | General | |
| R3-226656 | BL CR Assignment for Rel-18 SL Relay Enhancements WI | LG Electronics |
| 16.2 | Support Relay and Remote UE Authorization | |
| R3-226354 | Further discussion on multi-path authorization | ZTE |
| R3-226657 | [Draft] Reply LS on ProSe Authorization information related to UE-to-UE Relay operation to NG-RAN | LG Electronics |
| R3-226822 | Reply LS on ProSe Authorization information related to UE-to-UE Relay operation to NG-RAN | LG Electronics |
| 16.3 | Support Service Continuity Enhancements | |
| R3-226233 | Inter-gNB Service Continuity for L2 U2N Relay | Ericsson |
| R3-226264 | (TPs for BLCRs for TS 38.401 and TS 38.423): SL relay: Inter-gNB mobility | Huawei |
| R3-226273 | Selection of the target relay UE for service continuity | InterDigital |
| R3-226284 | Discussion on Service Continuity Enhancements for SL relay | CATT |
| R3-226313 | Discussion on Support Service Continuity Enhancements | Nokia, Nokia Shanghai Bell |
| R3-226392 | Service continuity enhancements for U2N relays | China Telecommunication |
| R3-226523 | Service continuity enhancements for L2 relays | Qualcomm Incorporated |
| R3-226588 | (TP to TS 38.401) Remaining issues on service continuity enhancement | Samsung |
| R3-226658 | (TP to TS 38.401 and 38.423) Consideration on service continuity enhancement for L2 U2N relay | LG Electronics |
| R3-226707 | Service continuity for U2N relay | CMCC |
| R3-226850 | CB: # 32_SLRelay_ServiceContinuity - Summary of email discussion | Samsung - moderator |
| 16.4 | Multi-path Support | |
| R3-226234 | Multi-path for Sidelink Relay | Ericsson |
| R3-226265 | SL relay: U2U relay and Multi-path relay | Huawei |
| R3-226285 | Discussion on Multi-path Support for SL relay | CATT |
| R3-226314 | discussion on the support for multi-path | Nokia, Nokia Shanghai Bell |
| R3-226355 | Remaining issues of multi-path relay and service continuinty for L2 U2N relay | ZTE |
| R3-226524 | Direct path and indirect path addition in multi-path relays | Qualcomm Incorporated |
| R3-226589 | (TP to TS 38.401) Remaining issues on multipath for sidelink relay | Samsung |
| R3-226659 | Consideration on multi-path support and U2U relay operation | LG Electronics |
| R3-226708 | Considerations on multi-path for SL relay | CMCC |
| 17.1 | General | |
| R3-226102 | UE Location Verification by the Network | Ericsson, CATT, Thales, Huawei, Samsung, ZTE, Nokia, Nokia Shanghai Bell |
| R3-226106 | XnAP BLCR on NTN Functionality | Huawei, Ericsson, Thales, ZTE, Omnispace, TTP, Nokia, Nokia Shanghai Bell, CATT, Hughes Network Systems, CMCC |
| R3-226166 | LS on Satellite coverage data transfer to a UE using UP versus CP | SA2 |
| 17.2 | Support Mobility and Service Continuity Enhancements | |
| R3-226272 | Xn interface enhancements in NTN | InterDigital |
| R3-226315 | Discussion on the Mobility and Service Continuity Enhancements in NR NTN | Nokia, Nokia Shanghai Bell |
| R3-226316 | [draft] LS on CHO with time-based trigger condition in N2-HO | Nokia, Nokia Shanghai Bell |
| R3-226393 | Further discussion on mobility enhancement of NTN | China Telecommunication |
| R3-226411 | Time-Based HO for NTN and NGAP | Ericsson LM |
| R3-226412 | Time-Based HO for NTN - NGAP impacts | Ericsson, Thales, ZTE, Omnispace, TTP, CATT, Hughes, EchoStar, Huawei |
| R3-226413 | Xn and NTN with Transparent Payload in Rel-18 | Ericsson LM |
| R3-226476 | Further discussion on mobility issue for NR NTN | ZTE |
| R3-226568 | Discussion Mobility and Service Continuity Enhancements for NTN | CATT |
| R3-226591 | Further discussion on service continuity enhancement | Samsung |
| R3-226619 | Further discussion on mobility of NTN | Huawei |
| R3-226620 | Further discussion on XN and NG interface | Huawei |
| R3-226649 | CR for TS38.300 on Clarification of Cell Identifier used for handover signalling and Xn Interface | Qualcomm Incorporated, Huawei, Nokia, ZTE, Deutsche Telekom, Verizon Wireless, CATT, NEC |
| R3-226655 | Discussion on NR NTN Service Continuity Enhancements | Qualcomm Incorporated |
| R3-226706 | Discussion on mobility enhancement of NTN | CMCC |
| R3-226770 | Time-Based HO for NTN and NGAP | Ericsson LM, Thales |
| R3-226859 | CB: # 41_NRNTN - Summary of email discussion | Nokia - moderator |
| 17.3 | Network verified UE location | |
| R3-226184 | Latency impact for NTN verified UE location | RAN2 |
| R3-226569 | Discussion on UE location verification for NR NTN | CATT |
| R3-226654 | NRPPa for Network Verified UE location | Qualcomm Incorporated |
| 18.1 | General | |
| R3-226929 | (BLCR to 36.300) IoT NTN enhancements | ZTE |
| 18.2 | Support discontinuous coverage | |
| R3-226317 | Discussion on the support for discontinuous coverage | Nokia, Nokia Shanghai Bell |
| R3-226318 | Support for IoT NTN enhancements | Nokia, Nokia Shanghai Bell, CATT, Thales, Ericsson, Huawei |
| R3-226444 | Discussion of SA2 SI Conclusions and Potential RAN3 Impacts | Ericsson, Thales, Huawei |
| R3-226445 | Time-Based CHO and IoT NTN | Ericsson LM |
| R3-226462 | Time-Based HO for IoT NTN - S1AP Impacts | Ericsson, Huawei |
| R3-226477 | Further discussion on discontinuous coverage issue for IoT NTN | ZTE |
| R3-226478 | Support of discontinuous coverage for IoT NTN | ZTE |
| R3-226594 | Discussion on the discontinuous coverage issues | Samsung |
| R3-226627 | Further discussion on the support of discontinuous coverage | Huawei |
| R3-226628 | Support for IoT NTN enhancements | Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson |
| R3-226629 | X2AP CR on IoT NTN Functionality | Huawei, CATT, Nokia, Nokia Shanghai Bell, Qualcomm, ZTE, CMCC, Ericsson |
| R3-226630 | S1AP impact to support discontinuous coverage | Huawei |
| R3-226634 | Discussion on the support of discontinuous coverage | CATT |
| R3-226771 | Time-Based HO for IoT NTN - S1AP Impacts | Ericsson, Huawei |
| R3-226864 | Support for IoT NTN enhancements | Nokia, Nokia Shanghai Bell, CATT, Thales, Ericsson, Huawei |
| R3-226865 | (TP BL CR 36.300) Support for IoT NTN enhancements | Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson, ZTE |
| R3-226924 | Support for IoT NTN enhancements | Nokia, Nokia Shanghai Bell, CATT, Thales, Ericsson, Huawei, ZTE |
| R3-226925 | (TP BL CR 36.300) Support for IoT NTN enhancements | Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson, ZTE |
| 19.1 | General | |
| R3-226404 | Uncrewed Aerial Vehicles in Rel-18 - updated workplan | Nokia, Nokia Shanghai Bell |
| 19.2 | Support Subscription-based Aerial-UE Identification | |
| R3-226198 | On subscription-based UAV UE identification | Nokia, Nokia Shanghai Bell |
| R3-226374 | UAV Support over NG-RAN interface | NEC |
| R3-226458 | Introduction of Aerial authorization information | Ericsson, AT&T, NTT DOCOMO, INC, Qualcomm Incorporated, Intel Corporation |
| R3-226459 | NR support for UAV WI | Ericsson |
| R3-226595 | Discussion on open issue for NR support for UAV | Samsung |
| R3-226616 | Further discussion on NR support for UAV | Huawei |
| R3-226617 | NR support for UAV over NG | Huawei, China Unicom, China Telecom, CATT |
| R3-226618 | NR support for UAV over Xn | Huawei, China Unicom, China Telecom, CATT |
| R3-226633 | Subscription based aerial UE identification in NGAP and XnAP | CATT |
| R3-226671 | Discussions on UAV identifications | Intel Corporation |
| R3-226752 | Discussion on NR support for UAV | ZTE |
| R3-226791 | CB: # 12_R18UAV - Summary of email discussion | Nokia - moderator |
| R3-226823 | Draft CR to 38.300 on NR support for UAV | Nokia, Nokia Shanghai Bell, Huawei, Intel Corporation, ZTE, Ericsson, Samsung, CATT, Qualcomm, Deutsche Telekom, NEC |
| R3-226840 | Introduction of Aerial authorization information | Ericsson, AT&T, NTT DOCOMO INC, Qualcomm Incorporated, Intel Corporation, Samsung, NEC, Nokia, Nokia Shanghai Bell, Huawei, ZTE, CATT |
| R3-226841 | NR support for UAV over Xn | Huawei, China Unicom, China Telecom, CATT, Intel Corporation, ZTE, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, Samsung |
| 22.2 | Support Network-Controlled Repeater Management | |
| R3-226174 | Reply LS on NCR Solutions | SA3 |
| R3-226270 | Management of Network-Controlled Repeater | Qualcomm Inc. |
| R3-226319 | Discussion on Identification and authorization of Network Controlled Repeater | Nokia, Nokia Shanghai Bell |
| R3-226320 | Stage-2 TP for NCR | Nokia, Nokia Shanghai Bell |
| R3-226325 | (TPs to TS 38.300, TS 38.413, TS 38.401 BL CRs) Support of Network-Controlled Repeater | Huawei |
| R3-226326 | Support of Network-Controlled Repeater | Huawei |
| R3-226375 | Down-selection of NCR management solutions | NEC |
| R3-226405 | Network-Controlled Repeater Authorization and Management | Ericsson LM |
| R3-226406 | Network-Controlled Repeaters Authorization - Solution 4 | Ericsson LM |
| R3-226571 | Discussion on NCR management | CATT |
| R3-226572 | CR for TS 38.413 Support NCR authorization | CATT |
| R3-226573 | Supporting Authorization for Network Controlled Repeater | Samsung |
| R3-226574 | Supporting NCR Device-OAM connectivity | Samsung |
| R3-226648 | Authorization for NR network-controlled repeaters | AT&T |
| R3-226684 | Why RAN validation is necessary | Intel Corporation |
| R3-226685 | [Draft] Reply LS on NCR validation | Intel Corporation |
| R3-226687 | Discussion on the Potential Solutions for Repeater Management | China Telecom |
| R3-226701 | Discussion on the network-controlled repeater management | CMCC |
| R3-226749 | Discussion on NCR management | ZTE |
| R3-226750 | Discussion on network architecture for NCR | ZTE |
| R3-226751 | [Draft] Reply LS on clarification for NCR validation | ZTE |
| R3-226814 | CB: # 26_NCR - Summary of email discussion | ZTE - moderator |
| R3-226824 | 38300 BL CR for Network Controlled Repeater management | ZTE, Samsung, CATT |
| R3-226825 | Network-Controlled Repeaters Authorization | Ericsson, CATT, Nokia, Nokia Shanghai Bell, Samsung, ZTE |
| R3-226923 | CB: # 26_NCR - Summary of email discussion | ZTE - moderator |
| R3-226926 | 38300 BL CR for Network Controlled Repeater management | ZTE, Samsung, CATT, Ericsson |
| 23.1 | General | |
| R3-226670 | Work Plan for Study Item on Expanded and Improved NR Positioning | Intel Corporation, CATT, Ericsson |
| 23.2 | Support Enhancements on NR Positioning | |
| R3-226171 | LS on RAN dependency for Ranging/Sidelink Positioning | SA2 |
| R3-226175 | Reply LS on Terminology Alignment for Ranging/Sidelink Positioning | RAN1 |
| R3-226180 | LS on SRS in multiple cells | RAN2 |
| R3-226183 | Reply LS on Terminology Alignment for Ranging/Sidelink Positioning | RAN2 |
| R3-226303 | Remaining Issues on R18 Positioning (TP included) | Huawei |
| R3-226304 | [DRAFT] Reply LS on LPHAP indication delivery to RAN | Huawei |
| R3-226305 | [DRAFT] Reply LS on SRS in multiple cells | Huawei |
| R3-226570 | Consideration on the incoming LSs from SA2 | CATT |
| R3-226590 | Conclusion on sidelink positioning SI | Samsung |
| R3-226734 | Reply LS on RAN dependency for Ranging and Sidelink Positioning | Xiaomi |
| R3-226746 | Discussion on the LS on sidelink positioning and LPHAP | ZTE |
| R3-226758 | Overview of the received Positioning LSes on Rel-18 Positioning | Ericsson |
| R3-226833 | TP to TR 38.859 capturing RAN3 Rel-18 Positioning SI agreements | Ericsson, Intel Corporation, Huawei, CATT, Samsung, ZTE, Nokia, Nokia Shanghai Bell, Xiaomi |
| R3-226834 | LS on Study on expanded and improved NR positioning | Huawei |
| R3-226887 | TP to TR 38.859 capturing RAN3 Rel-18 Positioning SI agreements | Ericsson, Intel Corporation, Huawei, CATT, Samsung, ZTE, Nokia, Nokia Shanghai Bell, Xiaomi |
| R3-226889 | LS on Study on expanded and improved NR positioning | Huawei |
| 24.1 | General | |
| R3-226397 | Work plan for NR network energy savings | Huawei |
| R3-226398 | Latest draft TR 38.864 v0.4.0 for information | Huawei |
| 24.2 | Support Network Energy Savings | |
| R3-226359 | TP for 38.864 on Network Energy Saving | CATT |
| R3-226399 | Network energy saving techniques | Huawei |
| R3-226457 | Discussion on Network Energy Saving SI | Ericsson |
| R3-226525 | Information exchange over network interfaces for network energy savings | Qualcomm Incorporated |
| R3-226532 | (TP for TR 38.864) Increased autonomy for cell switch-on/off in the gNB-DU | Nokia, Nokia Shanghai Bell |
| R3-226584 | Discussion on network energy saving | Samsung |
| R3-226669 | Considerations on network energy savings | Intel Corporation |
| R3-226754 | Discussion on NW ES and TP | ZTE |
| R3-226836 | CB: # 33_R18NetworkES - Summary of email discussion | Huawei - moderator |
| R3-226860 | Network energy saving techniques | Huawei, Intel Corporation, Ericsson |
| R3-226861 | Discussion on Network Energy Saving SI | Ericsson, Qualcomm Incorporated, Samsung, ZTE |
| R3-226862 | LS on network energy saving techniques | Huawei |
| R3-226897 | Network energy saving techniques | Huawei, Intel Corporation, Ericsson |
| R3-226898 | LS on network energy saving techniques | Huawei |
| 32 | Any other business | |
| R3-226266 | RRC container reference naming | Huawei, Ericsson |
| R3-226456 | [TP for TS 38.423] Proposed XnAP corrections of references to RRC | Ericsson |
| R3-226548 | (TP for TS 37.483) Proposed E1AP corrections of references to RRC | Ericsson |
| R3-226736 | [TP for TS 36.423] Proposed X2AP corrections of references to RRC | Ericsson |
| R3-226777 | RRC container reference naming | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm, Lenovo, Samsung, NEC |
| R3-226918 | Opening ceremony for RAN3#118 meeting | RAN3 chair |